More, precisely, it is a new major version zero (https://semver.org/).

Since I have merged #299 (dependency update), syncing up this branch with master will bring a change wrt v0.0.8-rc13. So, then, I'm fine considering that we can increment the version number and, hence, release v0.0.8!

I think this doesn't make sense, because then version 0.0.8-rc13 and version 0.0.8 are identical... whereas you would expect 0.0.8-rc13 < 0.0.8 (https://semver.org/).

Or maybe it does make sense, since any of the 0.0.8-rc* versions (release candidates) could have become version 0.0.8 after passing QA and assuming no change was needed... (not sure ;))

@mkcor Yeah, that was my logic! I figure that a (successful) release candidate shouldn't need to be modified for the release.